-
-
Notifications
You must be signed in to change notification settings - Fork 398
Identify managed platforms not tracked by a package index #2174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identify managed platforms not tracked by a package index #2174
Conversation
2306d9e
to
25ba5c8
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #2174 +/- ##
==========================================
+ Coverage 62.53% 63.34% +0.80%
==========================================
Files 223 223
Lines 19488 19663 +175
==========================================
+ Hits 12187 12455 +268
+ Misses 6210 6123 -87
+ Partials 1091 1085 -6
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
25ba5c8
to
d33e77d
Compare
799e3a5
to
c420bc0
Compare
c420bc0
to
621052d
Compare
9ecb877
to
605ac83
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some nitpicks, the PR looks good overall.
internal/cli/core/upgrade.go
Outdated
if response == nil || response.Platform == nil { | ||
return | ||
} | ||
if !response.Platform.Indexed || (response.Platform.MissingMetadata && !response.Platform.Indexed) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!Indexed || (MissingMetada && !Indexed)
is redundant you can just write: !Indexed
.
BTW, the case of MissingMetadata && !Indexed
is still valid and should print something along the line of:
Platform %s is missing installation metadata, it may not work properly or need re-installation.
but this should not be printed in the "core update" or "core install". The question is then, where to show it? maybe on compile or upload... Anyway, since all the required information is now available to the IDE via gRPC, I think we could merge this PR as-is and think about where to display the warning in a separate issue.
0382c1f
to
c184f20
Compare
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
We're introducing a warning message in the cli, when the user runs the upgrade of a platform that's no longer present in the additional-urls config.
We also modify a bit some proto messages.
What is the current behavior?
Right now when a platform is installed but the URL tracking the latest update for that platform gets removed from the config we're no longer to track the newest versions, and the user is not notified about it.
What is the new behavior?
When a platform is installed but the additional URL is no longer present In the config, we send a warning message in the stdout when the user tries to perform a core upgrade for that platform.
Protobuff changes:
message Platform
:message PlatformUpgradeResponse
:The rpc call
PlatformUpgrade
now also returns the Platform object which FE can use theindexed
andmissing_metadata
to display some warnings. Like:bonus:
Does this PR introduce a breaking change, and is titled accordingly?
nope
Other information
I think we should discuss if we need a system to track down various warning messages.